Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3b2a7dff0c57142d7470d46cb94db58596cee3abcef4319cd78ecd480ca4fc9

Tx prefix hash: a101bbea365818ccf7e168a966750b31b4e4965ab37f0214e180dadde2cfce66
Tx public key: 9b1101edfd8c6a24fa0f4e6a1875b2d2b7850cd2903fa05cd81524c748568ec8
Timestamp: 1736281782 Timestamp [UCT]: 2025-01-07 20:29:42 Age [y:d:h:m:s]: 00:159:17:49:11
Block: 1192404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113883 RingCT/type: yes/0
Extra: 019b1101edfd8c6a24fa0f4e6a1875b2d2b7850cd2903fa05cd81524c748568ec8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce078c6800531675d7a5d60c27f4e0a99536169a0f373ca55c15bc0c66e5ff9d 0.600000000000 1678955 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": 1192414, "vin": [ { "gen": { "height": 1192404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce078c6800531675d7a5d60c27f4e0a99536169a0f373ca55c15bc0c66e5ff9d" } } ], "extra": [ 1, 155, 17, 1, 237, 253, 140, 106, 36, 250, 15, 78, 106, 24, 117, 178, 210, 183, 133, 12, 210, 144, 63, 160, 92, 216, 21, 36, 199, 72, 86, 142, 200, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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