Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d300dc6a0b43dbe273ed6041991d78ee83422f77e14ece11ed0a806801c5fe7

Tx prefix hash: 40f7fd696c277b06012700fd027bf2cd279c2feae3f034b4a2a1237a82b74c9b
Tx public key: 0cea57db3e1455b1d8538923c6389c69d3464b20a39a095b0bf6fefde774e95e
Timestamp: 1706335517 Timestamp [UCT]: 2024-01-27 06:05:17 Age [y:d:h:m:s]: 01:288:11:13:14
Block: 944242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464979 RingCT/type: yes/0
Extra: 010cea57db3e1455b1d8538923c6389c69d3464b20a39a095b0bf6fefde774e95e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6f13889994600ef4f04cee8d9e2b0f5d7e9393acd3ee29a9d819062f5e0e452 0.600000000000 1402478 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": 944252, "vin": [ { "gen": { "height": 944242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6f13889994600ef4f04cee8d9e2b0f5d7e9393acd3ee29a9d819062f5e0e452" } } ], "extra": [ 1, 12, 234, 87, 219, 62, 20, 85, 177, 216, 83, 137, 35, 198, 56, 156, 105, 211, 70, 75, 32, 163, 154, 9, 91, 11, 246, 254, 253, 231, 116, 233, 94, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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