Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ecc80db50d341952fc4cfc16b5dc865bffc80fa7bb5d5ad01b0c328ca80e742

Tx prefix hash: 41c6807b333f00eb0005677ea40344dba3fdf9090391e3f9b3aaa647fafe761d
Tx public key: 3b04a4955065df527c8699dddccae33eeba6b27e10a88d7a0ba99e62410947eb
Timestamp: 1582434298 Timestamp [UCT]: 2020-02-23 05:04:58 Age [y:d:h:m:s]: 04:257:00:31:11
Block: 70596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076282 RingCT/type: yes/0
Extra: 013b04a4955065df527c8699dddccae33eeba6b27e10a88d7a0ba99e62410947eb02110000000b4ac5aa02000000000000000000

1 output(s) for total of 358.168137872000 dcy

stealth address amount amount idx
00: 5c030e4fe2c4f210e4023c7ad4077af8a0fa5d648a67965429ec95596c418f55 358.168137872000 130452 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": 70606, "vin": [ { "gen": { "height": 70596 } } ], "vout": [ { "amount": 358168137872, "target": { "key": "5c030e4fe2c4f210e4023c7ad4077af8a0fa5d648a67965429ec95596c418f55" } } ], "extra": [ 1, 59, 4, 164, 149, 80, 101, 223, 82, 124, 134, 153, 221, 220, 202, 227, 62, 235, 166, 178, 126, 16, 168, 141, 122, 11, 169, 158, 98, 65, 9, 71, 235, 2, 17, 0, 0, 0, 11, 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