Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7edd963636b49999d39d09fbef02b0064f2957b91014690d9597311da0bef25d

Tx prefix hash: ec96357211833b2a318d2dca5a6f3de4797ce669c7d4c289c4277b2c7c65c64a
Tx public key: 973c5c1e7ca60976c06ba02dd819b251cc018cd7c669a604eb47c5da8a05e198
Timestamp: 1728291988 Timestamp [UCT]: 2024-10-07 09:06:28 Age [y:d:h:m:s]: 00:209:09:06:27
Block: 1126301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149447 RingCT/type: yes/0
Extra: 01973c5c1e7ca60976c06ba02dd819b251cc018cd7c669a604eb47c5da8a05e19802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d217c4de9a6e4d7eb32e2a457aabb23ac434aa3c920ec23e8865129e25c39a5e 0.600000000000 1609090 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": 1126311, "vin": [ { "gen": { "height": 1126301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d217c4de9a6e4d7eb32e2a457aabb23ac434aa3c920ec23e8865129e25c39a5e" } } ], "extra": [ 1, 151, 60, 92, 30, 124, 166, 9, 118, 192, 107, 160, 45, 216, 25, 178, 81, 204, 1, 140, 215, 198, 105, 166, 4, 235, 71, 197, 218, 138, 5, 225, 152, 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