Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bfd4b83fa0cb3ac81eb53d4d8d65da898b20d1be3684c0ae8e2de05530f467e

Tx prefix hash: 4afcf1ac5c048479d39357afb7eb20f7eb197f7e6237fef09426c6d31a25523f
Tx public key: 7e954337b30ca661c1318ac559ad9c14fff4aae9d137500e3df271c9730888ea
Timestamp: 1733264308 Timestamp [UCT]: 2024-12-03 22:18:28 Age [y:d:h:m:s]: 00:201:05:45:59
Block: 1167421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143471 RingCT/type: yes/0
Extra: 017e954337b30ca661c1318ac559ad9c14fff4aae9d137500e3df271c9730888ea0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dffa373bd0341ed94bead617c5f496e107902d2c684a022b0735d73f91045ff 0.600000000000 1653116 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": 1167431, "vin": [ { "gen": { "height": 1167421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dffa373bd0341ed94bead617c5f496e107902d2c684a022b0735d73f91045ff" } } ], "extra": [ 1, 126, 149, 67, 55, 179, 12, 166, 97, 193, 49, 138, 197, 89, 173, 156, 20, 255, 244, 170, 233, 209, 55, 80, 14, 61, 242, 113, 201, 115, 8, 136, 234, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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