Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7f0d36d600c03e74aadb46f23cc2cc00932ca8f75bb353b32023ec2f7482d13

Tx prefix hash: ed524bbc38e14a84d7661a06aea266b940caa8d5018307004b6586cf8efb57e4
Tx public key: 1d3326080197857d3dcb937fb39cb4240a8c29ffcc0090afd459d917e4fb7219
Timestamp: 1702089670 Timestamp [UCT]: 2023-12-09 02:41:10 Age [y:d:h:m:s]: 01:039:06:58:44
Block: 909062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289452 RingCT/type: yes/0
Extra: 011d3326080197857d3dcb937fb39cb4240a8c29ffcc0090afd459d917e4fb7219021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b32871928e72017bd15257ef5e35c97667f3c360734c9332227e84c8a12e4d4d 0.600000000000 1366127 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": 909072, "vin": [ { "gen": { "height": 909062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b32871928e72017bd15257ef5e35c97667f3c360734c9332227e84c8a12e4d4d" } } ], "extra": [ 1, 29, 51, 38, 8, 1, 151, 133, 125, 61, 203, 147, 127, 179, 156, 180, 36, 10, 140, 41, 255, 204, 0, 144, 175, 212, 89, 217, 23, 228, 251, 114, 25, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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