Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35ad9b971585c18b00bb2596395a2b73576d439a0d08a96a4d33463a356bce3a

Tx prefix hash: f9795475fe52a5b6466fc8accc42f6289025a590077234b5cc3ed8eac668b5f7
Tx public key: 34d2c6247e69651f9e7c243c47fd7ef4417c4d3f31f34489c1187aa98e785a04
Timestamp: 1734447301 Timestamp [UCT]: 2024-12-17 14:55:01 Age [y:d:h:m:s]: 00:329:03:31:27
Block: 1177242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232733 RingCT/type: yes/0
Extra: 0134d2c6247e69651f9e7c243c47fd7ef4417c4d3f31f34489c1187aa98e785a04021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f9f81fae42f484cd7121c96a3a41fa9161fe3c3b58f93e9196138754d0c2352 0.600000000000 1663607 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": 1177252, "vin": [ { "gen": { "height": 1177242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f9f81fae42f484cd7121c96a3a41fa9161fe3c3b58f93e9196138754d0c2352" } } ], "extra": [ 1, 52, 210, 198, 36, 126, 105, 101, 31, 158, 124, 36, 60, 71, 253, 126, 244, 65, 124, 77, 63, 49, 243, 68, 137, 193, 24, 122, 169, 142, 120, 90, 4, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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