Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2da461a972b5b8ded8e04a94b292d41230c0a89b7b4875f5d7ac0b639c64ab55

Tx prefix hash: 45f95c0172399baa1b186766070579769d18c51394b1f589905464c928bc3b8c
Tx public key: 03be056c2239e436e4396929dc9a3c4537615c16e540f0f59fcfc4c80038b914
Timestamp: 1709913759 Timestamp [UCT]: 2024-03-08 16:02:39 Age [y:d:h:m:s]: 01:035:04:48:53
Block: 973939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286154 RingCT/type: yes/0
Extra: 0103be056c2239e436e4396929dc9a3c4537615c16e540f0f59fcfc4c80038b91402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 963ae6d6c4388f5ea09a3421e9ecc7567b0f939754dbab519d6183fdce276ca1 0.600000000000 1433882 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": 973949, "vin": [ { "gen": { "height": 973939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "963ae6d6c4388f5ea09a3421e9ecc7567b0f939754dbab519d6183fdce276ca1" } } ], "extra": [ 1, 3, 190, 5, 108, 34, 57, 228, 54, 228, 57, 105, 41, 220, 154, 60, 69, 55, 97, 92, 22, 229, 64, 240, 245, 159, 207, 196, 200, 0, 56, 185, 20, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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