Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd6c907e4151fa88be8d4d517c714f82d4992eb6399ab27741f0cad66007ae93

Tx prefix hash: 426b58286780018fcb14f7701c946d1f4dfdb912e4d5f2bc8e7864f73b50691f
Tx public key: 4b0524e4eefdd51e4e844608204ee94554804fa41735108a2c58a837f5dc5465
Timestamp: 1630107970 Timestamp [UCT]: 2021-08-27 23:46:10 Age [y:d:h:m:s]: 03:259:16:14:49
Block: 322140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 959987 RingCT/type: yes/0
Extra: 014b0524e4eefdd51e4e844608204ee94554804fa41735108a2c58a837f5dc546502110000001051fa4013000000000000000000

1 output(s) for total of 52.555347422000 dcy

stealth address amount amount idx
00: c36a95eb119f386c3ff5c239ea08ea5f720c71f6e97e6c8ca5452962c9a33484 52.555347422000 668548 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": 322150, "vin": [ { "gen": { "height": 322140 } } ], "vout": [ { "amount": 52555347422, "target": { "key": "c36a95eb119f386c3ff5c239ea08ea5f720c71f6e97e6c8ca5452962c9a33484" } } ], "extra": [ 1, 75, 5, 36, 228, 238, 253, 213, 30, 78, 132, 70, 8, 32, 78, 233, 69, 84, 128, 79, 164, 23, 53, 16, 138, 44, 88, 168, 55, 245, 220, 84, 101, 2, 17, 0, 0, 0, 16, 81, 250, 64, 19, 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