Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bcac36b95c0f2e71da5b502867d8d545d46188bd5b70bc81de79fbca5d3bd42

Tx prefix hash: f9ba62d8c7b26b2326d0bf5bf7e300f981e29eef13f95a49f01fa20b4b5ed3fe
Tx public key: f7827ec9ec84506925f0fabdd07ba27f696f70f06109ac3b5878817a03bcc693
Timestamp: 1717285951 Timestamp [UCT]: 2024-06-01 23:52:31 Age [y:d:h:m:s]: 00:348:00:05:53
Block: 1035060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248724 RingCT/type: yes/0
Extra: 01f7827ec9ec84506925f0fabdd07ba27f696f70f06109ac3b5878817a03bcc69302110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f5122cef0ce54c5a7a026c51a445b4e71e1d59270e894caf923a9826b745db5 0.600000000000 1503579 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": 1035070, "vin": [ { "gen": { "height": 1035060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f5122cef0ce54c5a7a026c51a445b4e71e1d59270e894caf923a9826b745db5" } } ], "extra": [ 1, 247, 130, 126, 201, 236, 132, 80, 105, 37, 240, 250, 189, 208, 123, 162, 127, 105, 111, 112, 240, 97, 9, 172, 59, 88, 120, 129, 122, 3, 188, 198, 147, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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