Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b020b7491d4faa7788cb2ba5ff48697ec3d66f93e0f732bf7c2fa3a9cef4f04

Tx prefix hash: 8c2573fdfe1768ebc917f19a3fee47e1a1bc934d6ba2848bc1a8f8770ca57ef2
Tx public key: 6b58e822e2ab79a0a4255cc63bc9f7c62be7a081f2170fbe73bdce27e4b1ab31
Timestamp: 1723499863 Timestamp [UCT]: 2024-08-12 21:57:43 Age [y:d:h:m:s]: 00:261:11:19:59
Block: 1086571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186767 RingCT/type: yes/0
Extra: 016b58e822e2ab79a0a4255cc63bc9f7c62be7a081f2170fbe73bdce27e4b1ab3102110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfd541bf8f3a8208c2ddad0ad330763f06d7d3a33e88f88e287d01ba66c36a26 0.600000000000 1561168 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": 1086581, "vin": [ { "gen": { "height": 1086571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfd541bf8f3a8208c2ddad0ad330763f06d7d3a33e88f88e287d01ba66c36a26" } } ], "extra": [ 1, 107, 88, 232, 34, 226, 171, 121, 160, 164, 37, 92, 198, 59, 201, 247, 198, 43, 231, 160, 129, 242, 23, 15, 190, 115, 189, 206, 39, 228, 177, 171, 49, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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