Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffbffc388acf08edc92bfe738eca13a7524f5891f3177f1422d04850cc735c85

Tx prefix hash: 36a649764984c93b3da3f5c911b635d754cbcdd4fd33f5eb3c3150d3d1c1a98d
Tx public key: 8bfded13139a48adc56a7a2ee500219cfe1ad4d5848663ce3995b68d94f5150a
Timestamp: 1579032270 Timestamp [UCT]: 2020-01-14 20:04:30 Age [y:d:h:m:s]: 05:120:13:18:41
Block: 45556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1236377 RingCT/type: yes/0
Extra: 018bfded13139a48adc56a7a2ee500219cfe1ad4d5848663ce3995b68d94f5150a0211000000da391a8d0e000000000000000000

1 output(s) for total of 433.565683092000 dcy

stealth address amount amount idx
00: a6ccd0d619825fd9dfdeb6b6bd6ae1f759cf3721c87700cfa61c834fa936a980 433.565683092000 83295 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": 45566, "vin": [ { "gen": { "height": 45556 } } ], "vout": [ { "amount": 433565683092, "target": { "key": "a6ccd0d619825fd9dfdeb6b6bd6ae1f759cf3721c87700cfa61c834fa936a980" } } ], "extra": [ 1, 139, 253, 237, 19, 19, 154, 72, 173, 197, 106, 122, 46, 229, 0, 33, 156, 254, 26, 212, 213, 132, 134, 99, 206, 57, 149, 182, 141, 148, 245, 21, 10, 2, 17, 0, 0, 0, 218, 57, 26, 141, 14, 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