Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c24e902929dfdc51853fbc41a5215a3a38b1ecd83f435b69c322f00649bc0a5

Tx prefix hash: 2ac3fcb04d1435c61a2029fd2388f3125fc60a58ed1b405063d3fc04bc6ca81a
Tx public key: bf7e760b2bfe73e695a8249f772423890b5dedf8dfa8aad6103be263b16d6e18
Timestamp: 1705718383 Timestamp [UCT]: 2024-01-20 02:39:43 Age [y:d:h:m:s]: 01:298:06:14:06
Block: 939122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472003 RingCT/type: yes/0
Extra: 01bf7e760b2bfe73e695a8249f772423890b5dedf8dfa8aad6103be263b16d6e180211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 179a1ffcc1ca361985a0d3e234d7bc2fdc38988631e91fb52e74e5196a7e5e06 0.600000000000 1397208 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": 939132, "vin": [ { "gen": { "height": 939122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "179a1ffcc1ca361985a0d3e234d7bc2fdc38988631e91fb52e74e5196a7e5e06" } } ], "extra": [ 1, 191, 126, 118, 11, 43, 254, 115, 230, 149, 168, 36, 159, 119, 36, 35, 137, 11, 93, 237, 248, 223, 168, 170, 214, 16, 59, 226, 99, 177, 109, 110, 24, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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