Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 487273c43afe89a0f5df16be44c92658ecdd0c6e4b07237b2a097166458f235f

Tx prefix hash: 467e36fff2000ac7ce9f17a575fd9d1a0c49610ea36740fb56d847e62396feaf
Tx public key: b35ca89608594bfa91595c67c26c3d830145d7e540628912ff9998b41c1669a7
Timestamp: 1715123236 Timestamp [UCT]: 2024-05-07 23:07:16 Age [y:d:h:m:s]: 00:327:18:38:39
Block: 1017128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234287 RingCT/type: yes/0
Extra: 01b35ca89608594bfa91595c67c26c3d830145d7e540628912ff9998b41c1669a70211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c1a733dcd2c0da6b2daaf8e075c33cae174bfb16ea9827b41b746b0eb704d4d 0.600000000000 1480895 of 15

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": 1017138, "vin": [ { "gen": { "height": 1017128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c1a733dcd2c0da6b2daaf8e075c33cae174bfb16ea9827b41b746b0eb704d4d" } } ], "extra": [ 1, 179, 92, 168, 150, 8, 89, 75, 250, 145, 89, 92, 103, 194, 108, 61, 131, 1, 69, 215, 229, 64, 98, 137, 18, 255, 153, 152, 180, 28, 22, 105, 167, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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