Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72c8c273ecfff06f55968cbd552a53b8057a1f3db2ef28abebe87c8bd7319191

Tx prefix hash: 1146d24ef70de719c214697e98b8dfc5e4ce08c36893f2874a50bbc5114c9f19
Tx public key: 7f5c327b092c48f6dd5095e87fb88ee04a9493ab9a2473de13527ab1f24b1e67
Timestamp: 1712633224 Timestamp [UCT]: 2024-04-09 03:27:04 Age [y:d:h:m:s]: 01:211:12:39:38
Block: 996455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409854 RingCT/type: yes/0
Extra: 017f5c327b092c48f6dd5095e87fb88ee04a9493ab9a2473de13527ab1f24b1e67021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73bda0a2e7b64db3549f2332c63adb5801aa12152feb7bde3267f1e89e6750b9 0.600000000000 1456873 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": 996465, "vin": [ { "gen": { "height": 996455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73bda0a2e7b64db3549f2332c63adb5801aa12152feb7bde3267f1e89e6750b9" } } ], "extra": [ 1, 127, 92, 50, 123, 9, 44, 72, 246, 221, 80, 149, 232, 127, 184, 142, 224, 74, 148, 147, 171, 154, 36, 115, 222, 19, 82, 122, 177, 242, 75, 30, 103, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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