Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1911497727802e12f0432aec2f537a4c380d4ab5f9bc2ac8afb51024e8b56a8a

Tx prefix hash: cd67db81c59865b0fbaa3b7d8297eed021ed5601f46ca3ec204507596df4dd6e
Tx public key: f6b864c449f4f2df52d6e405d8550cb63dcc8df6e2b33569622106d786fcb763
Timestamp: 1716301311 Timestamp [UCT]: 2024-05-21 14:21:51 Age [y:d:h:m:s]: 01:027:04:55:31
Block: 1026899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280250 RingCT/type: yes/0
Extra: 01f6b864c449f4f2df52d6e405d8550cb63dcc8df6e2b33569622106d786fcb76302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da229457782cffd2dcda6402908fe5132a0404aadf79e91e5cb6874e0d7da398 0.600000000000 1494234 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": 1026909, "vin": [ { "gen": { "height": 1026899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da229457782cffd2dcda6402908fe5132a0404aadf79e91e5cb6874e0d7da398" } } ], "extra": [ 1, 246, 184, 100, 196, 73, 244, 242, 223, 82, 214, 228, 5, 216, 85, 12, 182, 61, 204, 141, 246, 226, 179, 53, 105, 98, 33, 6, 215, 134, 252, 183, 99, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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