Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ace8b44f91d4ac62eb268f319d22bcc8563bad6436c8cf86e57f83fe6e59b3c6

Tx prefix hash: 2368df21a182fc5b9edea179028995d96a8010e60d8d6010b9ae41d2872ea929
Tx public key: e8fd3d1ddb662e912367887ada245f6878ef498b623bd75bf3fac44f19cedc7e
Timestamp: 1575384302 Timestamp [UCT]: 2019-12-03 14:45:02 Age [y:d:h:m:s]: 04:359:08:38:55
Block: 21485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1140242 RingCT/type: yes/0
Extra: 01e8fd3d1ddb662e912367887ada245f6878ef498b623bd75bf3fac44f19cedc7e020d3930303100010000006ac89603

1 output(s) for total of 520.969322943000 dcy

stealth address amount amount idx
00: ffa91e0982bab5e9678f9c4e9d4fb579d0429cd96979993226ee7cdb4898d92e 520.969322943000 34136 of 0

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": 21495, "vin": [ { "gen": { "height": 21485 } } ], "vout": [ { "amount": 520969322943, "target": { "key": "ffa91e0982bab5e9678f9c4e9d4fb579d0429cd96979993226ee7cdb4898d92e" } } ], "extra": [ 1, 232, 253, 61, 29, 219, 102, 46, 145, 35, 103, 136, 122, 218, 36, 95, 104, 120, 239, 73, 139, 98, 59, 215, 91, 243, 250, 196, 79, 25, 206, 220, 126, 2, 13, 57, 48, 48, 49, 0, 1, 0, 0, 0, 106, 200, 150, 3 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8