Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 498ef0219312d7169e76cde0e89aa583b8754e3c7b95b6bb5bf66fc05ab63fc7

Tx prefix hash: 67d91334a5e6524178bc39bfef90b31888566f5e374a51e3fa0166978d964962
Tx public key: 19ad58d554e1b5b257e403590345147f2853e583c983d4baa83d3013d44f6b7e
Timestamp: 1577637204 Timestamp [UCT]: 2019-12-29 16:33:24 Age [y:d:h:m:s]: 05:133:04:59:13
Block: 34417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1245010 RingCT/type: yes/0
Extra: 0119ad58d554e1b5b257e403590345147f2853e583c983d4baa83d3013d44f6b7e0211000000014ac5aa02000000000000000000

1 output(s) for total of 472.022877035000 dcy

stealth address amount amount idx
00: 4eef59584909f724c53333104347954efd188f0a08f4fa34a85ba396f9a087bc 472.022877035000 57927 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": 34427, "vin": [ { "gen": { "height": 34417 } } ], "vout": [ { "amount": 472022877035, "target": { "key": "4eef59584909f724c53333104347954efd188f0a08f4fa34a85ba396f9a087bc" } } ], "extra": [ 1, 25, 173, 88, 213, 84, 225, 181, 178, 87, 228, 3, 89, 3, 69, 20, 127, 40, 83, 229, 131, 201, 131, 212, 186, 168, 61, 48, 19, 212, 79, 107, 126, 2, 17, 0, 0, 0, 1, 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