Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 050227e4a32002d1847d59831d6128d492ad28e87bf84b5bb16575197d4f45dc

Tx prefix hash: e3106f73809552fb33e7c1ae7032eff37c30f2631e49a3c797591a4fbb267fb7
Tx public key: 0f03f1885254f6efc0a38c851d94e7467a1e3099f85f3adc22a78680993e041b
Timestamp: 1713087191 Timestamp [UCT]: 2024-04-14 09:33:11 Age [y:d:h:m:s]: 01:061:21:50:45
Block: 1000228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305161 RingCT/type: yes/0
Extra: 010f03f1885254f6efc0a38c851d94e7467a1e3099f85f3adc22a78680993e041b0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e00796d6c2145630d30bf7f4c9583cfd4e2a02a849eeac52e49072ef2a477b60 0.600000000000 1460724 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": 1000238, "vin": [ { "gen": { "height": 1000228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e00796d6c2145630d30bf7f4c9583cfd4e2a02a849eeac52e49072ef2a477b60" } } ], "extra": [ 1, 15, 3, 241, 136, 82, 84, 246, 239, 192, 163, 140, 133, 29, 148, 231, 70, 122, 30, 48, 153, 248, 95, 58, 220, 34, 167, 134, 128, 153, 62, 4, 27, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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