Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab506037db10b18ee94c33dbae253455f8a253edcb461f077a63c81b341e3e57

Tx prefix hash: 0655dedf3e97933ba211f75c7e9a41bff85669e8a85da32d628f28b12cca5814
Tx public key: 4ffdc2f5436267b27ece88367fc83f4cb3f83e72f8c08d060996587d5c58ef5f
Timestamp: 1574540801 Timestamp [UCT]: 2019-11-23 20:26:41 Age [y:d:h:m:s]: 05:079:00:49:25
Block: 15887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1199168 RingCT/type: yes/0
Extra: 014ffdc2f5436267b27ece88367fc83f4cb3f83e72f8c08d060996587d5c58ef5f02110000000c354bbe3b000000000000000000

1 output(s) for total of 543.701657347000 dcy

stealth address amount amount idx
00: 1da81321085b8ad56d58004e837a0a701940d8cec9c49d1f5a890c0a069cc31c 543.701657347000 21684 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": 15897, "vin": [ { "gen": { "height": 15887 } } ], "vout": [ { "amount": 543701657347, "target": { "key": "1da81321085b8ad56d58004e837a0a701940d8cec9c49d1f5a890c0a069cc31c" } } ], "extra": [ 1, 79, 253, 194, 245, 67, 98, 103, 178, 126, 206, 136, 54, 127, 200, 63, 76, 179, 248, 62, 114, 248, 192, 141, 6, 9, 150, 88, 125, 92, 88, 239, 95, 2, 17, 0, 0, 0, 12, 53, 75, 190, 59, 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