Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a1ea1066c367ab2217e270c19bf0b51f4fa6b0c975ed795d5a3af1bf3d87264

Tx prefix hash: 80eba765bea265714b990c2a5e8b878a6e01a01121f283962a4c1ec404b9af0a
Tx public key: 4c0a17787b244c1ae66ce6e88c204d22b1a8165e26475c332e625f0ad65f4cf8
Timestamp: 1574474751 Timestamp [UCT]: 2019-11-23 02:05:51 Age [y:d:h:m:s]: 05:077:09:06:01
Block: 14938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1198382 RingCT/type: yes/0
Extra: 014c0a17787b244c1ae66ce6e88c204d22b1a8165e26475c332e625f0ad65f4cf8021100000007b63f0b49000000000000000000

1 output(s) for total of 547.652518474000 dcy

stealth address amount amount idx
00: e402654d7dafcbe7b09341bf54129d3c4fcbb76a7f99c1fe7dbaf467d790c20e 547.652518474000 19534 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": 14948, "vin": [ { "gen": { "height": 14938 } } ], "vout": [ { "amount": 547652518474, "target": { "key": "e402654d7dafcbe7b09341bf54129d3c4fcbb76a7f99c1fe7dbaf467d790c20e" } } ], "extra": [ 1, 76, 10, 23, 120, 123, 36, 76, 26, 230, 108, 230, 232, 140, 32, 77, 34, 177, 168, 22, 94, 38, 71, 92, 51, 46, 98, 95, 10, 214, 95, 76, 248, 2, 17, 0, 0, 0, 7, 182, 63, 11, 73, 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