Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1410a9ed08e44831383216ac888933b83e8df829971f86b2b193d947b0679f1d

Tx prefix hash: d2c9dbfc5679d3f01ab1f58e07788983754de877ca60f9d0b4f955b23af7eff5
Tx public key: 74983ae5476e89a5c9ef80ab61d1cf55383daebfba01fb55c1aa375b84d6bfc2
Timestamp: 1729122644 Timestamp [UCT]: 2024-10-16 23:50:44 Age [y:d:h:m:s]: 00:148:04:24:49
Block: 1133189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105684 RingCT/type: yes/0
Extra: 0174983ae5476e89a5c9ef80ab61d1cf55383daebfba01fb55c1aa375b84d6bfc202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac1af4040c42c58328b7c9645446e3be21144e378d489f7a0edb0cb23f1bb357 0.600000000000 1616260 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": 1133199, "vin": [ { "gen": { "height": 1133189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac1af4040c42c58328b7c9645446e3be21144e378d489f7a0edb0cb23f1bb357" } } ], "extra": [ 1, 116, 152, 58, 229, 71, 110, 137, 165, 201, 239, 128, 171, 97, 209, 207, 85, 56, 61, 174, 191, 186, 1, 251, 85, 193, 170, 55, 91, 132, 214, 191, 194, 2, 17, 0, 0, 0, 5, 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