Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42c3695ee9bc25424805d51c940d4182591af7bcbec56cf934d1d68542899101

Tx prefix hash: cfd2de78250d8c48fa75371db109adfbd54aab57d8b1e3b91e6de1361d83491b
Tx public key: e3279f81c3e91f6ad30ae576872aa08885d3eb0dd3e37070c5a6dcc30651a046
Timestamp: 1639310751 Timestamp [UCT]: 2021-12-12 12:05:51 Age [y:d:h:m:s]: 02:331:04:26:20
Block: 393889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 754752 RingCT/type: yes/0
Extra: 01e3279f81c3e91f6ad30ae576872aa08885d3eb0dd3e37070c5a6dcc30651a046021100000001eaa12622000000000000000000

1 output(s) for total of 30.400630601000 dcy

stealth address amount amount idx
00: 0c7b96f3a65d16e3ca0b50e754468d77e6981e5c7c619fc5672214550ddd476e 30.400630601000 791270 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": 393899, "vin": [ { "gen": { "height": 393889 } } ], "vout": [ { "amount": 30400630601, "target": { "key": "0c7b96f3a65d16e3ca0b50e754468d77e6981e5c7c619fc5672214550ddd476e" } } ], "extra": [ 1, 227, 39, 159, 129, 195, 233, 31, 106, 211, 10, 229, 118, 135, 42, 160, 136, 133, 211, 235, 13, 211, 227, 112, 112, 197, 166, 220, 195, 6, 81, 160, 70, 2, 17, 0, 0, 0, 1, 234, 161, 38, 34, 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