Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46e8e6734c0360d0122a5f2d33aa280b92250275edbc4c24f5de86d81ba8663c

Tx prefix hash: 2e034a9c927b840f884ff3d2ef773fbfed37ba33494786d372b7e09c5d2869a1
Tx public key: 2ae2b10aacfb7219313bbf11d32b5bfd3a28ed71ddd4415788162cabea7048dc
Timestamp: 1714484777 Timestamp [UCT]: 2024-04-30 13:46:17 Age [y:d:h:m:s]: 01:013:19:55:30
Block: 1011824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270838 RingCT/type: yes/0
Extra: 012ae2b10aacfb7219313bbf11d32b5bfd3a28ed71ddd4415788162cabea7048dc0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22d18225090a7408c8fd5dcaab77d95429871e25e82e0c6df6bb39ab4491d23f 0.600000000000 1474160 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": 1011834, "vin": [ { "gen": { "height": 1011824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22d18225090a7408c8fd5dcaab77d95429871e25e82e0c6df6bb39ab4491d23f" } } ], "extra": [ 1, 42, 226, 177, 10, 172, 251, 114, 25, 49, 59, 191, 17, 211, 43, 91, 253, 58, 40, 237, 113, 221, 212, 65, 87, 136, 22, 44, 171, 234, 112, 72, 220, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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