Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb53dca418bc42d84bc3d7f9627ea920ca2ff6c6f8978a57029825538303351d

Tx prefix hash: 8c2a2ab2990c4a5e1a43f9332d1da78b2b420c324922fe9d207e7701378deb1e
Tx public key: 12e825bc06d7214bcc002f634b7c9a64f015243c98edd9fe985d249f27e648fb
Timestamp: 1708469139 Timestamp [UCT]: 2024-02-20 22:45:39 Age [y:d:h:m:s]: 01:261:14:02:55
Block: 961958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445697 RingCT/type: yes/0
Extra: 0112e825bc06d7214bcc002f634b7c9a64f015243c98edd9fe985d249f27e648fb021100000002d49b3c67000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3717e4c0c367dead16e222167f728620b7fb627fbc3fb54f083dfccdf5e0414 0.600000000000 1421577 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": 961968, "vin": [ { "gen": { "height": 961958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3717e4c0c367dead16e222167f728620b7fb627fbc3fb54f083dfccdf5e0414" } } ], "extra": [ 1, 18, 232, 37, 188, 6, 215, 33, 75, 204, 0, 47, 99, 75, 124, 154, 100, 240, 21, 36, 60, 152, 237, 217, 254, 152, 93, 36, 159, 39, 230, 72, 251, 2, 17, 0, 0, 0, 2, 212, 155, 60, 103, 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