Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a415aa88a48cdc82c79eaf9c6f006ed8a14c8099ab49ed28338041909d79c76

Tx prefix hash: 79a3821409fe1e97b66c1670a4ea5aa57e735a54acd5baa76d8bfcffe6de16be
Tx public key: 4c356ba1d14e271c45ac09c5a6e5877ebbe3ac6815cd44349ea1ac7dee251190
Timestamp: 1733711545 Timestamp [UCT]: 2024-12-09 02:32:25 Age [y:d:h:m:s]: 00:144:03:11:16
Block: 1171134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102812 RingCT/type: yes/0
Extra: 014c356ba1d14e271c45ac09c5a6e5877ebbe3ac6815cd44349ea1ac7dee251190021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b169e819b0f29c2bc2e0460c54c5ed13adcb6bdc3a7284abe4528863457068e7 0.600000000000 1656871 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": 1171144, "vin": [ { "gen": { "height": 1171134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b169e819b0f29c2bc2e0460c54c5ed13adcb6bdc3a7284abe4528863457068e7" } } ], "extra": [ 1, 76, 53, 107, 161, 209, 78, 39, 28, 69, 172, 9, 197, 166, 229, 135, 126, 187, 227, 172, 104, 21, 205, 68, 52, 158, 161, 172, 125, 238, 37, 17, 144, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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