Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 913070f5062d9797c6584e2a2e4d407a0f5efb2d784d003ae2d8d373799d7f8e

Tx prefix hash: b1cbe53a8ef157fd7d54ccbcb8e13fb1d45381af23ab07f98b6389de4340f6d3
Tx public key: b5ade6fe8ef804f0c265fd8bec8071de16a158daa196bb66b507991c5966f820
Timestamp: 1705641413 Timestamp [UCT]: 2024-01-19 05:16:53 Age [y:d:h:m:s]: 01:089:23:51:29
Block: 938494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325425 RingCT/type: yes/0
Extra: 01b5ade6fe8ef804f0c265fd8bec8071de16a158daa196bb66b507991c5966f8200211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7594e109450755405ca099b9386a84c6455190c0bdb4ab74bb5eb7d1f99f8ef1 0.600000000000 1396564 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": 938504, "vin": [ { "gen": { "height": 938494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7594e109450755405ca099b9386a84c6455190c0bdb4ab74bb5eb7d1f99f8ef1" } } ], "extra": [ 1, 181, 173, 230, 254, 142, 248, 4, 240, 194, 101, 253, 139, 236, 128, 113, 222, 22, 161, 88, 218, 161, 150, 187, 102, 181, 7, 153, 28, 89, 102, 248, 32, 2, 17, 0, 0, 0, 2, 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