Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c06e15a63d4ed1d995a3506f6ea5e1a00a236297718be5f3fe11eb0edce7f7df

Tx prefix hash: bd223ffb4f847c231ca5ec8485706d757a77ce491f41f28729d8656acd760ca1
Tx public key: 7a780451c90a7480c30dd76a220112d746ec3c5b373b715e41280b4eb577b429
Timestamp: 1717329109 Timestamp [UCT]: 2024-06-02 11:51:49 Age [y:d:h:m:s]: 00:313:10:47:05
Block: 1035423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224017 RingCT/type: yes/0
Extra: 017a780451c90a7480c30dd76a220112d746ec3c5b373b715e41280b4eb577b42902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 988ed2d62c07efc7d71b6368071c9eb2972fdbfbf8a448236d002712dd758ab7 0.600000000000 1503944 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": 1035433, "vin": [ { "gen": { "height": 1035423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "988ed2d62c07efc7d71b6368071c9eb2972fdbfbf8a448236d002712dd758ab7" } } ], "extra": [ 1, 122, 120, 4, 81, 201, 10, 116, 128, 195, 13, 215, 106, 34, 1, 18, 215, 70, 236, 60, 91, 55, 59, 113, 94, 65, 40, 11, 78, 181, 119, 180, 41, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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