Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ff5ab09db83614372b46c60003732ae906e6b4fbebd27a99acb5c1d3b5a723a

Tx prefix hash: e95c347c9af5f7533626e4c0f00ac5381bec303b41fa380d0cecd5fcdaa87c9b
Tx public key: 8d132f748e83fb5b3cb5ea2028f57a12e410e63e075eac7cf72b043e1a27d668
Timestamp: 1705173483 Timestamp [UCT]: 2024-01-13 19:18:03 Age [y:d:h:m:s]: 01:082:05:12:52
Block: 934623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319860 RingCT/type: yes/0
Extra: 018d132f748e83fb5b3cb5ea2028f57a12e410e63e075eac7cf72b043e1a27d66802110000000f7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4b07432981bf0b8365d1ac6004c3780dcf0241eb1a528aa9f50cfb647455176 0.600000000000 1392637 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": 934633, "vin": [ { "gen": { "height": 934623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4b07432981bf0b8365d1ac6004c3780dcf0241eb1a528aa9f50cfb647455176" } } ], "extra": [ 1, 141, 19, 47, 116, 142, 131, 251, 91, 60, 181, 234, 32, 40, 245, 122, 18, 228, 16, 230, 62, 7, 94, 172, 124, 247, 43, 4, 62, 26, 39, 214, 104, 2, 17, 0, 0, 0, 15, 122, 156, 244, 199, 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