Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7133aa63a38944a78ebd3160602655f64e599e5b07a109f9a0a2d29af439fa7

Tx prefix hash: d472960688df3bddc965f578736a71b192466115fa03bf9a94fc8eaa1d9ed6b0
Tx public key: 4bb44b9d9e23926dc796a153185df4b68bf97c80baf309434ac683d357794909
Timestamp: 1722226373 Timestamp [UCT]: 2024-07-29 04:12:53 Age [y:d:h:m:s]: 00:263:01:34:00
Block: 1076016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187921 RingCT/type: yes/0
Extra: 014bb44b9d9e23926dc796a153185df4b68bf97c80baf309434ac683d357794909021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7ffca68a322cffc39fc954e9a4a7b674c3d15a0beb01a1dfe25c80c0add1f01 0.600000000000 1548551 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": 1076026, "vin": [ { "gen": { "height": 1076016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7ffca68a322cffc39fc954e9a4a7b674c3d15a0beb01a1dfe25c80c0add1f01" } } ], "extra": [ 1, 75, 180, 75, 157, 158, 35, 146, 109, 199, 150, 161, 83, 24, 93, 244, 182, 139, 249, 124, 128, 186, 243, 9, 67, 74, 198, 131, 211, 87, 121, 73, 9, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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