Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcfcae2a716996877d9317cb965632ee130295a899507969eb8317d62e0691d1

Tx prefix hash: 7aa5d16e66bd54243cfbcc73cb6bb5ded48b8b9e65c0a8f42032ce3d1ef0eeae
Tx public key: f371a6ce8c7c0a12792d911f83d88cddaeee3e5b610eb4a9b1e08b4b9c6e1ab1
Timestamp: 1577685851 Timestamp [UCT]: 2019-12-30 06:04:11 Age [y:d:h:m:s]: 04:363:16:35:02
Block: 34816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149065 RingCT/type: yes/0
Extra: 01f371a6ce8c7c0a12792d911f83d88cddaeee3e5b610eb4a9b1e08b4b9c6e1ab102110000000e8a2ee0d9000000000000000000

1 output(s) for total of 470.588158151000 dcy

stealth address amount amount idx
00: cb12026b1eb99814708ca520c9e1cfcc53ffdd9683a86bbdc3954040d13878d7 470.588158151000 58647 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": 34826, "vin": [ { "gen": { "height": 34816 } } ], "vout": [ { "amount": 470588158151, "target": { "key": "cb12026b1eb99814708ca520c9e1cfcc53ffdd9683a86bbdc3954040d13878d7" } } ], "extra": [ 1, 243, 113, 166, 206, 140, 124, 10, 18, 121, 45, 145, 31, 131, 216, 140, 221, 174, 238, 62, 91, 97, 14, 180, 169, 177, 224, 139, 75, 156, 110, 26, 177, 2, 17, 0, 0, 0, 14, 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