Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 849f4b321dd3aee1ae25ab076cec66959dcd708e31c6758959a5eca69bbb3796

Tx prefix hash: 499f6bcacf7588264c72f78f1c047c56ff9f7dab355ae8f5ba4148b7523d1875
Tx public key: 273d00c827d7146cbb1eb7f05f3eaaa4a00f24812bb03f7656ae9e41c55da4a2
Timestamp: 1713531265 Timestamp [UCT]: 2024-04-19 12:54:25 Age [y:d:h:m:s]: 00:208:21:02:40
Block: 1003921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149530 RingCT/type: yes/0
Extra: 01273d00c827d7146cbb1eb7f05f3eaaa4a00f24812bb03f7656ae9e41c55da4a20211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae3dc102cd938671b1c1a717cf8d622c017dcfbc6b11dca4884b9528f8252049 0.600000000000 1464471 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": 1003931, "vin": [ { "gen": { "height": 1003921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae3dc102cd938671b1c1a717cf8d622c017dcfbc6b11dca4884b9528f8252049" } } ], "extra": [ 1, 39, 61, 0, 200, 39, 215, 20, 108, 187, 30, 183, 240, 95, 62, 170, 164, 160, 15, 36, 129, 43, 176, 63, 118, 86, 174, 158, 65, 197, 93, 164, 162, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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