Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16c1fc65949722e89dbf67e1f87d8aa3cbfc0bcd7ddd6ff105e67af11f4177c9

Tx prefix hash: 94c64e850adc849d07b22172600a504274f2eb7433dc1df8ecd0e6fa18dfc4d7
Tx public key: 355175ef8d84bd7b520e374b18a23e91a39ed43dd0b16a417f53295b6f9343fc
Timestamp: 1725803669 Timestamp [UCT]: 2024-09-08 13:54:29 Age [y:d:h:m:s]: 00:076:07:41:27
Block: 1105671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54564 RingCT/type: yes/0
Extra: 01355175ef8d84bd7b520e374b18a23e91a39ed43dd0b16a417f53295b6f9343fc021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0be4b7683155b875a17954d2cbfe3f352546708a7d73856c22f3a7aa7c82e330 0.600000000000 1583090 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": 1105681, "vin": [ { "gen": { "height": 1105671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0be4b7683155b875a17954d2cbfe3f352546708a7d73856c22f3a7aa7c82e330" } } ], "extra": [ 1, 53, 81, 117, 239, 141, 132, 189, 123, 82, 14, 55, 75, 24, 162, 62, 145, 163, 158, 212, 61, 208, 177, 106, 65, 127, 83, 41, 91, 111, 147, 67, 252, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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