Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7357de9db20d23b8f262e911c948c470da5af6ebc6708665b755b858997e0d9a

Tx prefix hash: 274ad44815d52bc8fee7678bb2fde557ebda87dd217d80e9a50dd0efde6b0f48
Tx public key: 71fb6f2d4511ae9b588be2e1a8b03f7d80594371116808d024351b0b1582fb02
Timestamp: 1727486771 Timestamp [UCT]: 2024-09-28 01:26:11 Age [y:d:h:m:s]: 00:116:16:47:49
Block: 1119626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83396 RingCT/type: yes/0
Extra: 0171fb6f2d4511ae9b588be2e1a8b03f7d80594371116808d024351b0b1582fb0202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03a591dce3384c077b619c47249b308b70e46b97e271cd7a58814f66413f90eb 0.600000000000 1601253 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": 1119636, "vin": [ { "gen": { "height": 1119626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03a591dce3384c077b619c47249b308b70e46b97e271cd7a58814f66413f90eb" } } ], "extra": [ 1, 113, 251, 111, 45, 69, 17, 174, 155, 88, 139, 226, 225, 168, 176, 63, 125, 128, 89, 67, 113, 17, 104, 8, 208, 36, 53, 27, 11, 21, 130, 251, 2, 2, 17, 0, 0, 0, 6, 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