Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2454fc9b035a1d8a45f312ccc0afc7a68e3035f1dd4a6f411e378a61381beb7

Tx prefix hash: c29e3abc089dd0b98a68545136d93457f4dfe5d07607cb682ee0fc0b0184bed8
Tx public key: 42406549c8420c7f887b8dfe63653e24a76ffab92f16f3b6a0126a9d0a0f95a5
Timestamp: 1674649645 Timestamp [UCT]: 2023-01-25 12:27:25 Age [y:d:h:m:s]: 01:341:19:02:27
Block: 682456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505265 RingCT/type: yes/0
Extra: 0142406549c8420c7f887b8dfe63653e24a76ffab92f16f3b6a0126a9d0a0f95a5021100000003e6d27f9c000000000000000000

1 output(s) for total of 3.363100999000 dcy

stealth address amount amount idx
00: 4e612c98003f7b7eae48265db919e64fbea4f6ad66c3c8dbf350a0a41f47f745 3.363100999000 1124579 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": 682466, "vin": [ { "gen": { "height": 682456 } } ], "vout": [ { "amount": 3363100999, "target": { "key": "4e612c98003f7b7eae48265db919e64fbea4f6ad66c3c8dbf350a0a41f47f745" } } ], "extra": [ 1, 66, 64, 101, 73, 200, 66, 12, 127, 136, 123, 141, 254, 99, 101, 62, 36, 167, 111, 250, 185, 47, 22, 243, 182, 160, 18, 106, 157, 10, 15, 149, 165, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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