Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bfe0e402fd6bcd7cd98b7284a76566aab008b081c1a6df8b44dd45bae0026a8

Tx prefix hash: ad16fe49972f6888645d0db445fb47ba356e9b41058d5b341066efd017d84fca
Tx public key: 5f088ec83510366eafa9c1137c35af29b20c2eced3501d730a877d07ae3bf0b1
Timestamp: 1577728770 Timestamp [UCT]: 2019-12-30 17:59:30 Age [y:d:h:m:s]: 05:071:16:41:43
Block: 35214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200991 RingCT/type: yes/0
Extra: 015f088ec83510366eafa9c1137c35af29b20c2eced3501d730a877d07ae3bf0b10211000000064ac5aa02000000000000000000

1 output(s) for total of 469.161379527000 dcy

stealth address amount amount idx
00: e8957e01c4fd8c1d67c8b2f7a516fb7f93fd6453053b5e7a03f3da88ba8184f6 469.161379527000 59304 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": 35224, "vin": [ { "gen": { "height": 35214 } } ], "vout": [ { "amount": 469161379527, "target": { "key": "e8957e01c4fd8c1d67c8b2f7a516fb7f93fd6453053b5e7a03f3da88ba8184f6" } } ], "extra": [ 1, 95, 8, 142, 200, 53, 16, 54, 110, 175, 169, 193, 19, 124, 53, 175, 41, 178, 12, 46, 206, 211, 80, 29, 115, 10, 135, 125, 7, 174, 59, 240, 177, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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