Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd9fb3f15f5aefd2ed3ebd8dd29e357881e1ce2423ae815621d1aee97f2c86f3

Tx prefix hash: e9b06c52f6864ef7171e7295005a99f821358e1a1c1352d210506f26abeb49b6
Tx public key: 7a208d7b46d2db17dc462e043928623c5ecdca63c7e88a48981c528fd8f0e09e
Timestamp: 1722102849 Timestamp [UCT]: 2024-07-27 17:54:09 Age [y:d:h:m:s]: 00:241:13:35:52
Block: 1074987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172541 RingCT/type: yes/0
Extra: 017a208d7b46d2db17dc462e043928623c5ecdca63c7e88a48981c528fd8f0e09e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaff0b670ce387df37c2b4d2a547dcd9cfbf064e4cbb6914cc0c5acb325314ee 0.600000000000 1547506 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": 1074997, "vin": [ { "gen": { "height": 1074987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaff0b670ce387df37c2b4d2a547dcd9cfbf064e4cbb6914cc0c5acb325314ee" } } ], "extra": [ 1, 122, 32, 141, 123, 70, 210, 219, 23, 220, 70, 46, 4, 57, 40, 98, 60, 94, 205, 202, 99, 199, 232, 138, 72, 152, 28, 82, 143, 216, 240, 224, 158, 2, 17, 0, 0, 0, 3, 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