Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: febd6bc4f813f41613108b024b44f3a8390b3dc3bfc75b9670e66f7954182f2d

Tx prefix hash: 89a11201424a385f990d7528de54ddb561e8537e9a2d68e4f8b0ecf8102783eb
Tx public key: ff47923bbfb7fa4af47829efaf785c3d8a132e325d19c2c68ea710c7135bb8d2
Timestamp: 1721610725 Timestamp [UCT]: 2024-07-22 01:12:05 Age [y:d:h:m:s]: 00:276:16:50:24
Block: 1070903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197695 RingCT/type: yes/0
Extra: 01ff47923bbfb7fa4af47829efaf785c3d8a132e325d19c2c68ea710c7135bb8d2021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c9303ea3a790e068ccf223c41f16ebf6eea0bfec44841d8c17f9d816b0289d9 0.600000000000 1542926 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": 1070913, "vin": [ { "gen": { "height": 1070903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c9303ea3a790e068ccf223c41f16ebf6eea0bfec44841d8c17f9d816b0289d9" } } ], "extra": [ 1, 255, 71, 146, 59, 191, 183, 250, 74, 244, 120, 41, 239, 175, 120, 92, 61, 138, 19, 46, 50, 93, 25, 194, 198, 142, 167, 16, 199, 19, 91, 184, 210, 2, 17, 0, 0, 0, 4, 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