Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0378ca58c419aebe15fdb51f7ff7e98a4052bcac4bf51ebb3817bca0152103c6

Tx prefix hash: 7d75719773d145f74d7de11cd7a8907fb6e535445c848978c97bf9578e449274
Tx public key: bb4e2b6019f0c9d0829c58847e75bfa9949382383dd3d0e7cf6647d52aa18274
Timestamp: 1719859193 Timestamp [UCT]: 2024-07-01 18:39:53 Age [y:d:h:m:s]: 00:353:00:54:24
Block: 1056380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252194 RingCT/type: yes/0
Extra: 01bb4e2b6019f0c9d0829c58847e75bfa9949382383dd3d0e7cf6647d52aa182740211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f795f44e7eedcab6bcb67e21b4f088d2db0823e55d1e7a366470f8cb9779e4f1 0.600000000000 1526793 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": 1056390, "vin": [ { "gen": { "height": 1056380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f795f44e7eedcab6bcb67e21b4f088d2db0823e55d1e7a366470f8cb9779e4f1" } } ], "extra": [ 1, 187, 78, 43, 96, 25, 240, 201, 208, 130, 156, 88, 132, 126, 117, 191, 169, 148, 147, 130, 56, 61, 211, 208, 231, 207, 102, 71, 213, 42, 161, 130, 116, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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