Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3588a589e8b73c493db45264987d1070848a6c28a42fab43c2c22e46683e8b14

Tx prefix hash: cc6ecfecce126944fb008939e3551abc727fa8727d781f058f87394f9517100f
Tx public key: 361dc9a8cf8621db30f45d712e2e69a43fa111bea82993b7a74db95cb95bd9c5
Timestamp: 1719257148 Timestamp [UCT]: 2024-06-24 19:25:48 Age [y:d:h:m:s]: 01:134:19:06:11
Block: 1051383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354877 RingCT/type: yes/0
Extra: 01361dc9a8cf8621db30f45d712e2e69a43fa111bea82993b7a74db95cb95bd9c502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2c74e1614f3ef5dde9e3181348719d8e2a3261031270f621a6227a54b61c5bf 0.600000000000 1521694 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": 1051393, "vin": [ { "gen": { "height": 1051383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2c74e1614f3ef5dde9e3181348719d8e2a3261031270f621a6227a54b61c5bf" } } ], "extra": [ 1, 54, 29, 201, 168, 207, 134, 33, 219, 48, 244, 93, 113, 46, 46, 105, 164, 63, 161, 17, 190, 168, 41, 147, 183, 167, 77, 185, 92, 185, 91, 217, 197, 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