Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f3829637f8ba07856ce6c425c6fd8630814c0c04a7f9b9c24ef1e873998cf11

Tx prefix hash: aa8617294d539d8494cd8181d75961dfdc7580d01585d95489337bf7d56975b9
Tx public key: 7e73214c9aff16cd2cce48e72829e9a05c23947278cb055e6b80b7ed435b8c94
Timestamp: 1720742103 Timestamp [UCT]: 2024-07-11 23:55:03 Age [y:d:h:m:s]: 00:338:11:43:12
Block: 1063712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241795 RingCT/type: yes/0
Extra: 017e73214c9aff16cd2cce48e72829e9a05c23947278cb055e6b80b7ed435b8c9402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f5a7eda703e3570facb76f0851a0aac6351e050f70de38ad9a5a66932f74e94 0.600000000000 1534229 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": 1063722, "vin": [ { "gen": { "height": 1063712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f5a7eda703e3570facb76f0851a0aac6351e050f70de38ad9a5a66932f74e94" } } ], "extra": [ 1, 126, 115, 33, 76, 154, 255, 22, 205, 44, 206, 72, 231, 40, 41, 233, 160, 92, 35, 148, 114, 120, 203, 5, 94, 107, 128, 183, 237, 67, 91, 140, 148, 2, 17, 0, 0, 0, 3, 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