Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bfdd44a900671aed4731544819d8d3ec329e50af3832860d80ebea7bb259c0e

Tx prefix hash: c31cf69e412371d95a03ece1393e07863fd426ffc0b44bf62ba63985a9a95104
Tx public key: 6fece5ac60acfc0e8165d4b074aaa1e05c084786ff0589896d763f6df1356070
Timestamp: 1578656440 Timestamp [UCT]: 2020-01-10 11:40:40 Age [y:d:h:m:s]: 04:351:08:03:20
Block: 42603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140485 RingCT/type: yes/0
Extra: 016fece5ac60acfc0e8165d4b074aaa1e05c084786ff0589896d763f6df13560700211000000084ac5aa02000000000000000000

1 output(s) for total of 443.444649811000 dcy

stealth address amount amount idx
00: c135393ceef79aa066bbf1f335df619a6130a3c71f2ee66b61eaa3e22b1e08c5 443.444649811000 76810 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": 42613, "vin": [ { "gen": { "height": 42603 } } ], "vout": [ { "amount": 443444649811, "target": { "key": "c135393ceef79aa066bbf1f335df619a6130a3c71f2ee66b61eaa3e22b1e08c5" } } ], "extra": [ 1, 111, 236, 229, 172, 96, 172, 252, 14, 129, 101, 212, 176, 116, 170, 161, 224, 92, 8, 71, 134, 255, 5, 137, 137, 109, 118, 63, 109, 241, 53, 96, 112, 2, 17, 0, 0, 0, 8, 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