Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b931a2287254ced6483d3053b31a994d2177e90490da449bb3dc2526b6eb8b26

Tx prefix hash: 2a3d18d31816e4c971039c953acdc998b74a55b9c725756bc607a3b1b13374c6
Tx public key: 90006c69f2e1dc725783bb0c79e89069c69be8288b5e99f170d83b67230910d7
Timestamp: 1577185295 Timestamp [UCT]: 2019-12-24 11:01:35 Age [y:d:h:m:s]: 05:152:15:43:43
Block: 30622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1258992 RingCT/type: yes/0
Extra: 0190006c69f2e1dc725783bb0c79e89069c69be8288b5e99f170d83b67230910d7021100000021ac34bf9e000000000000000000

1 output(s) for total of 485.889443446000 dcy

stealth address amount amount idx
00: d4adb280565cbb40b13ac8e2dee71a52fac0eadcb81e84c396ccd2739d402f92 485.889443446000 50564 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": 30632, "vin": [ { "gen": { "height": 30622 } } ], "vout": [ { "amount": 485889443446, "target": { "key": "d4adb280565cbb40b13ac8e2dee71a52fac0eadcb81e84c396ccd2739d402f92" } } ], "extra": [ 1, 144, 0, 108, 105, 242, 225, 220, 114, 87, 131, 187, 12, 121, 232, 144, 105, 198, 155, 232, 40, 139, 94, 153, 241, 112, 216, 59, 103, 35, 9, 16, 215, 2, 17, 0, 0, 0, 33, 172, 52, 191, 158, 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