Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc336ab2a32e183c10ef80baf568720d5e0cf89703bfc63cf28e45bf963281d7

Tx prefix hash: 1f244679a93bd90757de4569f44b10d7171ed0c2470b738313de5423878cd0ab
Tx public key: 17fadc6ad2d7e5da915335b0f41163fd4f96c77ec2ae837bb36a818817ea5e2c
Timestamp: 1736655544 Timestamp [UCT]: 2025-01-12 04:19:04 Age [y:d:h:m:s]: 00:157:12:52:08
Block: 1195493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112299 RingCT/type: yes/0
Extra: 0117fadc6ad2d7e5da915335b0f41163fd4f96c77ec2ae837bb36a818817ea5e2c02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79f7c72febb787c56b0e6c37a462e45d73e34aaed50c95888b63ec0f6bae4f0f 0.600000000000 1682084 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": 1195503, "vin": [ { "gen": { "height": 1195493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79f7c72febb787c56b0e6c37a462e45d73e34aaed50c95888b63ec0f6bae4f0f" } } ], "extra": [ 1, 23, 250, 220, 106, 210, 215, 229, 218, 145, 83, 53, 176, 244, 17, 99, 253, 79, 150, 199, 126, 194, 174, 131, 123, 179, 106, 129, 136, 23, 234, 94, 44, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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