Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b990ec96b8259124e358387b1b04b82da9e2e8cdf84c5f2f0d0f58f5985f137e

Tx prefix hash: ef3ab17c62fb262a1906172fa1a22cf62597ea897825c24d7150ed2ae51f789e
Tx public key: 0fbd7472882777f9fcca2947d79b1f3d1b85572ad369ced8dc20fa0ff9308aa0
Timestamp: 1725454329 Timestamp [UCT]: 2024-09-04 12:52:09 Age [y:d:h:m:s]: 00:126:17:03:20
Block: 1102782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90619 RingCT/type: yes/0
Extra: 010fbd7472882777f9fcca2947d79b1f3d1b85572ad369ced8dc20fa0ff9308aa002110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb77a4787e64a814aeefd1c17c4d1d5c96a8b1ea52967afc42d519180028dcba 0.600000000000 1579349 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": 1102792, "vin": [ { "gen": { "height": 1102782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb77a4787e64a814aeefd1c17c4d1d5c96a8b1ea52967afc42d519180028dcba" } } ], "extra": [ 1, 15, 189, 116, 114, 136, 39, 119, 249, 252, 202, 41, 71, 215, 155, 31, 61, 27, 133, 87, 42, 211, 105, 206, 216, 220, 32, 250, 15, 249, 48, 138, 160, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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