Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7662ee7f8a1d8652b178de3ac31107b44f792f09a6abb46986baf914acac84

Tx prefix hash: efdb882b4bb26c0a6c43f7ed1d37eb80da1f0a27740c30970527e7969f6fb8f1
Tx public key: 27e9aa40ad3a48a9bee7d43ad7674103698b8a28a1dd69e642427371626d1888
Timestamp: 1726125815 Timestamp [UCT]: 2024-09-12 07:23:35 Age [y:d:h:m:s]: 00:225:05:14:54
Block: 1108333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160819 RingCT/type: yes/0
Extra: 0127e9aa40ad3a48a9bee7d43ad7674103698b8a28a1dd69e642427371626d188802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d15995911694e6b55d4f100e513224d7f05db62dcd2c1709a90af3e05b09fc77 0.600000000000 1586192 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": 1108343, "vin": [ { "gen": { "height": 1108333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d15995911694e6b55d4f100e513224d7f05db62dcd2c1709a90af3e05b09fc77" } } ], "extra": [ 1, 39, 233, 170, 64, 173, 58, 72, 169, 190, 231, 212, 58, 215, 103, 65, 3, 105, 139, 138, 40, 161, 221, 105, 230, 66, 66, 115, 113, 98, 109, 24, 136, 2, 17, 0, 0, 0, 5, 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