Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9315cdcdc2dfea3dec2a59213b201ef01fcaba79d8e535ff7cc3d90a62f68f29

Tx prefix hash: 474f29cd5217e1458a6b6de6f3dafca23624f2d45e3d0d52e7303a9ba8f20a8f
Tx public key: aa4e2ff0aa7bd8a81f31e7804bbd3729061f689a2cff9102bd1764dbc9240b8c
Timestamp: 1738387490 Timestamp [UCT]: 2025-02-01 05:24:50 Age [y:d:h:m:s]: 00:328:23:28:15
Block: 1209572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232935 RingCT/type: yes/0
Extra: 01aa4e2ff0aa7bd8a81f31e7804bbd3729061f689a2cff9102bd1764dbc9240b8c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41583386e98045e656c5ddb99974bc3c5351a45077137fbaa2f9b16169be5294 0.600000000000 1696317 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": 1209582, "vin": [ { "gen": { "height": 1209572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41583386e98045e656c5ddb99974bc3c5351a45077137fbaa2f9b16169be5294" } } ], "extra": [ 1, 170, 78, 47, 240, 170, 123, 216, 168, 31, 49, 231, 128, 75, 189, 55, 41, 6, 31, 104, 154, 44, 255, 145, 2, 189, 23, 100, 219, 201, 36, 11, 140, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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