Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdcae1570874e7807a87b170c6324c015fc59c310d193d550ca03db879499cfb

Tx prefix hash: 2cb2cc1cddc05d67ab82fd5f5e96fb54872f804e73b34bea0f4bc444b6c16efa
Tx public key: 24a1bf89e8aa11fe10ba9ef99f5133a96db8e7735e6167aa787e06c24085b6f6
Timestamp: 1738448405 Timestamp [UCT]: 2025-02-01 22:20:05 Age [y:d:h:m:s]: 00:292:00:07:54
Block: 1210067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206463 RingCT/type: yes/0
Extra: 0124a1bf89e8aa11fe10ba9ef99f5133a96db8e7735e6167aa787e06c24085b6f60211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6745fd1b2e16c6971708a33a186c5b6b89595e96ef2dd985a64237626e9d1181 0.600000000000 1696814 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": 1210077, "vin": [ { "gen": { "height": 1210067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6745fd1b2e16c6971708a33a186c5b6b89595e96ef2dd985a64237626e9d1181" } } ], "extra": [ 1, 36, 161, 191, 137, 232, 170, 17, 254, 16, 186, 158, 249, 159, 81, 51, 169, 109, 184, 231, 115, 94, 97, 103, 170, 120, 126, 6, 194, 64, 133, 182, 246, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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