Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cdf497f6805d0c454693bfec2f5a13e34867f8360681a70a21a8e314d8ebd95

Tx prefix hash: 683f27050f07b8d3d7b8a779ad8c139a3a020a2c8507a697d9e209d68398985e
Tx public key: 25ee264cf764736d478430845f01083a6e7bb53d08151897aa4bc6c2e2d3d8f2
Timestamp: 1732336138 Timestamp [UCT]: 2024-11-23 04:28:58 Age [y:d:h:m:s]: 00:001:02:57:10
Block: 1159722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 813 RingCT/type: yes/0
Extra: 0125ee264cf764736d478430845f01083a6e7bb53d08151897aa4bc6c2e2d3d8f2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d91c00f4c83cadb1dc5dc9ff6c1af3c58824edad4766bfcbdb1d252d1ec3ca7 0.600000000000 1645361 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": 1159732, "vin": [ { "gen": { "height": 1159722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d91c00f4c83cadb1dc5dc9ff6c1af3c58824edad4766bfcbdb1d252d1ec3ca7" } } ], "extra": [ 1, 37, 238, 38, 76, 247, 100, 115, 109, 71, 132, 48, 132, 95, 1, 8, 58, 110, 123, 181, 61, 8, 21, 24, 151, 170, 75, 198, 194, 226, 211, 216, 242, 2, 17, 0, 0, 0, 3, 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