Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa50888cba9203dd7a697e3fea908a8cd1af39fe93d3de4b65af3c5b85f9562d

Tx prefix hash: 179b14fc4f2726b1a95f56e51e623a157a8b5496c3195786133e7b7f83fb405d
Tx public key: 5208f7abb083667432aa2bdebe36e116e48c3d095379ce15d989c708282d8e68
Timestamp: 1588734015 Timestamp [UCT]: 2020-05-06 03:00:15 Age [y:d:h:m:s]: 04:303:09:34:53
Block: 98691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133264 RingCT/type: yes/0
Extra: 015208f7abb083667432aa2bdebe36e116e48c3d095379ce15d989c708282d8e68021100000003209b4bc8000000000000000000

1 output(s) for total of 289.065666781000 dcy

stealth address amount amount idx
00: 6b785e65245edb967b1701a1ac91cce22e77536d4445832075e6876dc0ce4b5e 289.065666781000 174417 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": 98701, "vin": [ { "gen": { "height": 98691 } } ], "vout": [ { "amount": 289065666781, "target": { "key": "6b785e65245edb967b1701a1ac91cce22e77536d4445832075e6876dc0ce4b5e" } } ], "extra": [ 1, 82, 8, 247, 171, 176, 131, 102, 116, 50, 170, 43, 222, 190, 54, 225, 22, 228, 140, 61, 9, 83, 121, 206, 21, 217, 137, 199, 8, 40, 45, 142, 104, 2, 17, 0, 0, 0, 3, 32, 155, 75, 200, 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