Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56c9b3da14c5e85590081807d6310049e1695414ae9e7b095652ff769f6df7a2

Tx prefix hash: 92187eb3f508100906f3043ffd49715ce92709c9029ea4952f25f1a929d25ebc
Tx public key: a4e9a71c5ddfc7b08edfa70904b65f8fbb1edc987b5d751efac802e54de728c8
Timestamp: 1731975872 Timestamp [UCT]: 2024-11-19 00:24:32 Age [y:d:h:m:s]: 01:001:20:08:31
Block: 1156753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259718 RingCT/type: yes/0
Extra: 01a4e9a71c5ddfc7b08edfa70904b65f8fbb1edc987b5d751efac802e54de728c80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41cb9bd4ecb9bad57436ba9ffb0d836c0f287c5000bb121f87c6f11b481d6f51 0.600000000000 1642376 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": 1156763, "vin": [ { "gen": { "height": 1156753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41cb9bd4ecb9bad57436ba9ffb0d836c0f287c5000bb121f87c6f11b481d6f51" } } ], "extra": [ 1, 164, 233, 167, 28, 93, 223, 199, 176, 142, 223, 167, 9, 4, 182, 95, 143, 187, 30, 220, 152, 123, 93, 117, 30, 250, 200, 2, 229, 77, 231, 40, 200, 2, 17, 0, 0, 0, 4, 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