Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc78b28d592f2bdbb28f09dce2d564d196ee7e02b00d24f15619f0a85bf9b9f6

Tx prefix hash: 4204e7b4087905b330bdc14110b3c1d13cc00a93e622bba3994b0ba2e11c31d0
Tx public key: 7fc87372c677c1f01467c7da864bddbd34ac7cfe33493f7266b40fa271d611c5
Timestamp: 1650547165 Timestamp [UCT]: 2022-04-21 13:19:25 Age [y:d:h:m:s]: 03:016:13:55:40
Block: 484977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 792474 RingCT/type: yes/0
Extra: 017fc87372c677c1f01467c7da864bddbd34ac7cfe33493f7266b40fa271d611c502110000000133af99f4000000000000000000

1 output(s) for total of 15.172952666000 dcy

stealth address amount amount idx
00: 8c0562b45d6d3b04a039dcbe806435952882e440bd3cb46c1d99c2796166a6b4 15.172952666000 906960 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": 484987, "vin": [ { "gen": { "height": 484977 } } ], "vout": [ { "amount": 15172952666, "target": { "key": "8c0562b45d6d3b04a039dcbe806435952882e440bd3cb46c1d99c2796166a6b4" } } ], "extra": [ 1, 127, 200, 115, 114, 198, 119, 193, 240, 20, 103, 199, 218, 134, 75, 221, 189, 52, 172, 124, 254, 51, 73, 63, 114, 102, 180, 15, 162, 113, 214, 17, 197, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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