Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cfe39409c9f2bf52977e692dc585323e4cdec8c70f22709b1fe5506cbff3d23

Tx prefix hash: 229defc09d68f32bbf434781a69f95a84ffc6b2925d71c7e40cbd5b14d6d9224
Tx public key: 014040085f4644e02c382a4d0c2e35edbd7feb01ce704e72553459a25ea84c50
Timestamp: 1740930455 Timestamp [UCT]: 2025-03-02 15:47:35 Age [y:d:h:m:s]: 00:256:15:57:30
Block: 1230615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181194 RingCT/type: yes/0
Extra: 01014040085f4644e02c382a4d0c2e35edbd7feb01ce704e72553459a25ea84c500211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a0bb14ed8ade9cec2714449a13763edfde943ddf4a3d6d70c0500c822c34d12 0.600000000000 1717514 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": 1230625, "vin": [ { "gen": { "height": 1230615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a0bb14ed8ade9cec2714449a13763edfde943ddf4a3d6d70c0500c822c34d12" } } ], "extra": [ 1, 1, 64, 64, 8, 95, 70, 68, 224, 44, 56, 42, 77, 12, 46, 53, 237, 189, 127, 235, 1, 206, 112, 78, 114, 85, 52, 89, 162, 94, 168, 76, 80, 2, 17, 0, 0, 0, 5, 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