Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 114ed7f04a37c667a7676a3084110049a71491334e3dfdb74ae1a1cedcb272e0

Tx prefix hash: b4e439242e011d1e18ddd5c48b3946adfe4130163c9ee7cdc276cfcd07e424cd
Tx public key: 8ae39f9c09f0124eeda120050874b0a9a98b76819e09e40dbd7eece7b71e90dd
Timestamp: 1634299219 Timestamp [UCT]: 2021-10-15 12:00:19 Age [y:d:h:m:s]: 03:194:04:41:04
Block: 353556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 916437 RingCT/type: yes/0
Extra: 018ae39f9c09f0124eeda120050874b0a9a98b76819e09e40dbd7eece7b71e90dd02110000000c3fc41461000000000000000000

1 output(s) for total of 41.354485525000 dcy

stealth address amount amount idx
00: 95f75b6fb2d61e8cdb45cc465e637cb2766215fd0e7fb776f70a4227bfe118a5 41.354485525000 722440 of 0

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": 353566, "vin": [ { "gen": { "height": 353556 } } ], "vout": [ { "amount": 41354485525, "target": { "key": "95f75b6fb2d61e8cdb45cc465e637cb2766215fd0e7fb776f70a4227bfe118a5" } } ], "extra": [ 1, 138, 227, 159, 156, 9, 240, 18, 78, 237, 161, 32, 5, 8, 116, 176, 169, 169, 139, 118, 129, 158, 9, 228, 13, 189, 126, 236, 231, 183, 30, 144, 221, 2, 17, 0, 0, 0, 12, 63, 196, 20, 97, 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