Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 125ea3f976267736773c26cdeea6a4a915db3cc4f354efff66bba1af393e30d7

Tx prefix hash: 821ee8027b76628958448bff8ba3d245d44b20b667f53e0379fff0da58f5adb7
Tx public key: 3a2edac6731b4ebb2f4ede90ee2cf855c677c72b198db3b4c6c461e6ef0aa1be
Timestamp: 1709180438 Timestamp [UCT]: 2024-02-29 04:20:38 Age [y:d:h:m:s]: 01:091:00:42:24
Block: 967861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326109 RingCT/type: yes/0
Extra: 013a2edac6731b4ebb2f4ede90ee2cf855c677c72b198db3b4c6c461e6ef0aa1be0211000000010546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ef54d81844d60afb214d7cdae5522c822cf7ab5529ccc2b875ade7e643741ef 0.600000000000 1427652 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": 967871, "vin": [ { "gen": { "height": 967861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ef54d81844d60afb214d7cdae5522c822cf7ab5529ccc2b875ade7e643741ef" } } ], "extra": [ 1, 58, 46, 218, 198, 115, 27, 78, 187, 47, 78, 222, 144, 238, 44, 248, 85, 198, 119, 199, 43, 25, 141, 179, 180, 198, 196, 97, 230, 239, 10, 161, 190, 2, 17, 0, 0, 0, 1, 5, 70, 215, 208, 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