Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68cdc798e1fa8910873b5999bd321c9104bec50aa3b47bcd175acb3ca246af3f

Tx prefix hash: c95e08e145f0f521b28f01f5ab9609e4a6760ff188396e6e8637228e52f0d46f
Tx public key: 2ba637d6ddcb9e15e4a841f371ba3f9b06af06a6987b6b31878683b1d323a44a
Timestamp: 1736385592 Timestamp [UCT]: 2025-01-09 01:19:52 Age [y:d:h:m:s]: 00:162:10:23:01
Block: 1193267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115748 RingCT/type: yes/0
Extra: 012ba637d6ddcb9e15e4a841f371ba3f9b06af06a6987b6b31878683b1d323a44a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93249b88e541339e039376d58153fca4f263490275e5f3811d49952052f692e5 0.600000000000 1679826 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": 1193277, "vin": [ { "gen": { "height": 1193267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93249b88e541339e039376d58153fca4f263490275e5f3811d49952052f692e5" } } ], "extra": [ 1, 43, 166, 55, 214, 221, 203, 158, 21, 228, 168, 65, 243, 113, 186, 63, 155, 6, 175, 6, 166, 152, 123, 107, 49, 135, 134, 131, 177, 211, 35, 164, 74, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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