Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b810cd2464947e4512bb20f9d863d4f4dc7f057d0a8532e9a93a7e41ce7d883

Tx prefix hash: 0b28784fd8d310c19e56d3a3c6ee328efe5fe439747c80c58d420f1c4f9f5232
Tx public key: 575a941348f94f399645532921b6c9f795a97f00c2a278eb6c5074facec02765
Timestamp: 1705489637 Timestamp [UCT]: 2024-01-17 11:07:17 Age [y:d:h:m:s]: 01:152:10:18:10
Block: 937238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369967 RingCT/type: yes/0
Extra: 01575a941348f94f399645532921b6c9f795a97f00c2a278eb6c5074facec0276502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a50de88f305a73b7648ac05986d1f5cafdea380620fed1c89e6c5563b828a8b5 0.600000000000 1395282 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": 937248, "vin": [ { "gen": { "height": 937238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a50de88f305a73b7648ac05986d1f5cafdea380620fed1c89e6c5563b828a8b5" } } ], "extra": [ 1, 87, 90, 148, 19, 72, 249, 79, 57, 150, 69, 83, 41, 33, 182, 201, 247, 149, 169, 127, 0, 194, 162, 120, 235, 108, 80, 116, 250, 206, 192, 39, 101, 2, 17, 0, 0, 0, 3, 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