Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d37f4c1fdea14587b03ba0459d5aa945c7efb67aa18b04bce47385950f05593

Tx prefix hash: 6aa4d33e12831f99e2f6ce444253e6ca7f27676aa7b69835eb673c5356ef3a75
Tx public key: 35f0f50791b87b9c5a5b7815211f5728e8bd360b11939493ec207f2658ba7e7e
Timestamp: 1728676957 Timestamp [UCT]: 2024-10-11 20:02:37 Age [y:d:h:m:s]: 00:165:16:23:20
Block: 1129491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118186 RingCT/type: yes/0
Extra: 0135f0f50791b87b9c5a5b7815211f5728e8bd360b11939493ec207f2658ba7e7e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51da2a69f361f4d234cc5a528fbea560a5e226aed95047e779a3f42fbc49b691 0.600000000000 1612318 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": 1129501, "vin": [ { "gen": { "height": 1129491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51da2a69f361f4d234cc5a528fbea560a5e226aed95047e779a3f42fbc49b691" } } ], "extra": [ 1, 53, 240, 245, 7, 145, 184, 123, 156, 90, 91, 120, 21, 33, 31, 87, 40, 232, 189, 54, 11, 17, 147, 148, 147, 236, 32, 127, 38, 88, 186, 126, 126, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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