Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e32b0237aeea725c519fd07bb46d67c9e843a4174e491045d06b1bfe42bbc955

Tx prefix hash: fc3535da56b7143c26a016dd0a728cefdee0bdc2aae2ef6387bf2418a9a13be9
Tx public key: 58f77af0c146ca3e6c3808e59b54dce264a60534d8d249e58c138e1c3c6eba9e
Timestamp: 1581497671 Timestamp [UCT]: 2020-02-12 08:54:31 Age [y:d:h:m:s]: 05:090:20:56:05
Block: 63334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1217772 RingCT/type: yes/0
Extra: 0158f77af0c146ca3e6c3808e59b54dce264a60534d8d249e58c138e1c3c6eba9e021100000007d81c26c0000000000000000000

1 output(s) for total of 378.572427820000 dcy

stealth address amount amount idx
00: a2728796657bd38fc52dbb0dc51f04b65316ddf486a28dfcb6d3ffd928d5cd5e 378.572427820000 116792 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": 63344, "vin": [ { "gen": { "height": 63334 } } ], "vout": [ { "amount": 378572427820, "target": { "key": "a2728796657bd38fc52dbb0dc51f04b65316ddf486a28dfcb6d3ffd928d5cd5e" } } ], "extra": [ 1, 88, 247, 122, 240, 193, 70, 202, 62, 108, 56, 8, 229, 155, 84, 220, 226, 100, 166, 5, 52, 216, 210, 73, 229, 140, 19, 142, 28, 60, 110, 186, 158, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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