Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7cbf7b66ce0306fef102c917d6a4e7912d7d21e0db84c0ee8638270a99fa357

Tx prefix hash: d171afd5363623767929c2465f0cb5deea7df5310c654ab2932a2e4249a8474a
Tx public key: 232dceb8bb47e41ad9ef138eaa6d5fefaced23e99f6ad0dc57fd0a8e89114e78
Timestamp: 1580119046 Timestamp [UCT]: 2020-01-27 09:57:26 Age [y:d:h:m:s]: 04:304:14:27:16
Block: 53928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107826 RingCT/type: yes/0
Extra: 01232dceb8bb47e41ad9ef138eaa6d5fefaced23e99f6ad0dc57fd0a8e89114e78021100000051b221b3d1000000000000000000

1 output(s) for total of 406.738213394000 dcy

stealth address amount amount idx
00: a716b567892503fb1d6a025f9d4f5b37f44a2de98ae2d8e38a0bfba0dc148a43 406.738213394000 99915 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": 53938, "vin": [ { "gen": { "height": 53928 } } ], "vout": [ { "amount": 406738213394, "target": { "key": "a716b567892503fb1d6a025f9d4f5b37f44a2de98ae2d8e38a0bfba0dc148a43" } } ], "extra": [ 1, 35, 45, 206, 184, 187, 71, 228, 26, 217, 239, 19, 142, 170, 109, 95, 239, 172, 237, 35, 233, 159, 106, 208, 220, 87, 253, 10, 142, 137, 17, 78, 120, 2, 17, 0, 0, 0, 81, 178, 33, 179, 209, 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