Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac528d70b4d8b129e044c377a6baecfd09b5856fd1be6cb872562839f07f7c11

Tx prefix hash: 08f9863cec182800efbe7f63e84b04f055f8faa3b46179040652d745a38cd9db
Tx public key: 68720d4fd46f3450c940aafedcea159bd968805d019bdb9e1037170e8a3dfd97
Timestamp: 1578929215 Timestamp [UCT]: 2020-01-13 15:26:55 Age [y:d:h:m:s]: 05:052:06:39:21
Block: 44761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1187477 RingCT/type: yes/0
Extra: 0168720d4fd46f3450c940aafedcea159bd968805d019bdb9e1037170e8a3dfd970211000000138a2ee0d9000000000000000000

1 output(s) for total of 436.203420195000 dcy

stealth address amount amount idx
00: 04467f0b6fef8abe85376fe31da68a0613b4d4718ec56a7431da04a7431ee2c3 436.203420195000 81540 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": 44771, "vin": [ { "gen": { "height": 44761 } } ], "vout": [ { "amount": 436203420195, "target": { "key": "04467f0b6fef8abe85376fe31da68a0613b4d4718ec56a7431da04a7431ee2c3" } } ], "extra": [ 1, 104, 114, 13, 79, 212, 111, 52, 80, 201, 64, 170, 254, 220, 234, 21, 155, 217, 104, 128, 93, 1, 155, 219, 158, 16, 55, 23, 14, 138, 61, 253, 151, 2, 17, 0, 0, 0, 19, 138, 46, 224, 217, 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