Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36e8f636b9a4507fcd1eae2ccc2e3126bf5c361f38595b49ccdcd1fec98a7bd3

Tx prefix hash: b773664f14361a8cbdc11631cf4405c836538d6e95b520c32a1dc7067aa7b483
Tx public key: fb2ae40dfe005bfdc48c04ebf11f8628fbfcec1363b8281f85f201a1bdf3763e
Timestamp: 1579193071 Timestamp [UCT]: 2020-01-16 16:44:31 Age [y:d:h:m:s]: 05:056:13:22:40
Block: 46953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190533 RingCT/type: yes/0
Extra: 01fb2ae40dfe005bfdc48c04ebf11f8628fbfcec1363b8281f85f201a1bdf3763e0211000000038a2ee0d9000000000000000000

1 output(s) for total of 428.969147038000 dcy

stealth address amount amount idx
00: f2a40882ca678ea258bcdeb27c45ba0b65ba5cb61399af5920bfe38266299dc7 428.969147038000 86619 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": 46963, "vin": [ { "gen": { "height": 46953 } } ], "vout": [ { "amount": 428969147038, "target": { "key": "f2a40882ca678ea258bcdeb27c45ba0b65ba5cb61399af5920bfe38266299dc7" } } ], "extra": [ 1, 251, 42, 228, 13, 254, 0, 91, 253, 196, 140, 4, 235, 241, 31, 134, 40, 251, 252, 236, 19, 99, 184, 40, 31, 133, 242, 1, 161, 189, 243, 118, 62, 2, 17, 0, 0, 0, 3, 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