Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b2389792847c039a621d492fbf3244d056b29c630edb09df4db6db2bf539d4c

Tx prefix hash: aea1732e2e0e40ac76f544aab5a3a229117b91c41d33236bc23502c0ce167b16
Tx public key: 7a47a2a683c98ae874a3ee39db3d80ac9c8c9e24c7f0d0ad327970fed84f04ef
Timestamp: 1698382148 Timestamp [UCT]: 2023-10-27 04:49:08 Age [y:d:h:m:s]: 02:011:03:52:57
Block: 878554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527528 RingCT/type: yes/0
Extra: 017a47a2a683c98ae874a3ee39db3d80ac9c8c9e24c7f0d0ad327970fed84f04ef0211000000044b8f5122000000000000000000

1 output(s) for total of 0.753331119000 dcy

stealth address amount amount idx
00: e53b8e2d78665f43ed9d8a79fc1ca1c2e89b94064cb1b6439d715cb7f1b5b09a 0.753331119000 1334006 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": 878564, "vin": [ { "gen": { "height": 878554 } } ], "vout": [ { "amount": 753331119, "target": { "key": "e53b8e2d78665f43ed9d8a79fc1ca1c2e89b94064cb1b6439d715cb7f1b5b09a" } } ], "extra": [ 1, 122, 71, 162, 166, 131, 201, 138, 232, 116, 163, 238, 57, 219, 61, 128, 172, 156, 140, 158, 36, 199, 240, 208, 173, 50, 121, 112, 254, 216, 79, 4, 239, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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