Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: db7989942975f774149fbaf4b049507a6b34e478c6e66d0a053e7c540e00a03f

Tx prefix hash: c5bf7c2eae9dfa9f1feb07a5b51c1a6edf56b26939fe1cdb52d3a3cf9ad65929
Tx public key: 748ec68f2a4f81dd29a67c0493249f22f86b8d761f804ef860641e654e35a315
Timestamp: 1717497676 Timestamp [UCT]: 2024-06-04 10:41:16 Age [y:d:h:m:s]: 00:240:07:39:18
Block: 1036822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 171710 RingCT/type: yes/0
Extra: 01748ec68f2a4f81dd29a67c0493249f22f86b8d761f804ef860641e654e35a315

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a31eb55105cf1ff7aaad4d5af6072931ff41ccd629c85fe4f1d6f1af413061ad 0.600000000000 1505351 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1036832, "vin": [ { "gen": { "height": 1036822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a31eb55105cf1ff7aaad4d5af6072931ff41ccd629c85fe4f1d6f1af413061ad" } } ], "extra": [ 1, 116, 142, 198, 143, 42, 79, 129, 221, 41, 166, 124, 4, 147, 36, 159, 34, 248, 107, 141, 118, 31, 128, 78, 248, 96, 100, 30, 101, 78, 53, 163, 21 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8