Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff3dbac3a22be96d053b3ddc140200fb84890e9f1f15dc227094336529bde6cc

Tx prefix hash: c79bfaa9b4e2a75c2fe65e2642e3308a844849522615e5e7a68940d991fec4ca
Tx public key: 10ca7e7a5da5f443c743be523e88160fd37b16ecdd765b4981ceb9a807606a37
Timestamp: 1722604090 Timestamp [UCT]: 2024-08-02 13:08:10 Age [y:d:h:m:s]: 00:118:01:49:37
Block: 1079145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84489 RingCT/type: yes/0
Extra: 0110ca7e7a5da5f443c743be523e88160fd37b16ecdd765b4981ceb9a807606a37021100000004ef5a8513000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b75f79b4267ef999a5c8c095cc32ee8b3d9fb32b5430aae3e5b273e60e3af7e 0.600000000000 1551970 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": 1079155, "vin": [ { "gen": { "height": 1079145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b75f79b4267ef999a5c8c095cc32ee8b3d9fb32b5430aae3e5b273e60e3af7e" } } ], "extra": [ 1, 16, 202, 126, 122, 93, 165, 244, 67, 199, 67, 190, 82, 62, 136, 22, 15, 211, 123, 22, 236, 221, 118, 91, 73, 129, 206, 185, 168, 7, 96, 106, 55, 2, 17, 0, 0, 0, 4, 239, 90, 133, 19, 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