Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e0d42307dad51a4c2800849effe5b124bdb993faf00b6e2ddb95969f9531983

Tx prefix hash: 39f50367c4599b4900c51399546c2a524c9c9c84da127eb7c44379c5b9fc7861
Tx public key: a486b6a1f915bf2d7b26181525a0e23e61f8ff4dd90f6f44275c1718a63e045a
Timestamp: 1728416427 Timestamp [UCT]: 2024-10-08 19:40:27 Age [y:d:h:m:s]: 01:031:11:33:02
Block: 1127333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280870 RingCT/type: yes/0
Extra: 01a486b6a1f915bf2d7b26181525a0e23e61f8ff4dd90f6f44275c1718a63e045a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 392885916cef09855b8208f0b74e5e543c335b3330c4954a789d16a7a68065b1 0.600000000000 1610136 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": 1127343, "vin": [ { "gen": { "height": 1127333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "392885916cef09855b8208f0b74e5e543c335b3330c4954a789d16a7a68065b1" } } ], "extra": [ 1, 164, 134, 182, 161, 249, 21, 191, 45, 123, 38, 24, 21, 37, 160, 226, 62, 97, 248, 255, 77, 217, 15, 111, 68, 39, 92, 23, 24, 166, 62, 4, 90, 2, 17, 0, 0, 0, 3, 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